-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aa/cdh: make agent-config path configurable by env #429
aa/cdh: make agent-config path configurable by env #429
Conversation
9d36ccc
to
a124e80
Compare
fixes: confidential-containers#1637 blocked-by: confidential-containers/guest-components#429 On a podvm using an guest-components build from the PR, `KATA_AGENT_CONFIG_PATH` is set and picked up by attestation-agent and cdh: ```bash $ cat /proc/$(pgrep -i attest)/environ | xargs --null echo LANG=C.UTF-8 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin SYSTEMD_SULOGIN_FORCE=1 INVOCATION_ID=ad04b8c4ff6c4f2c8617dfcfed24c183 JOURNAL_STREAM=8:3090 SYSTEMD_EXEC_PID=552 KATA_AGENT_CONFIG_PATH=/run/peerpod/agent-config.toml RUST_BACKTRACE=full OCICRYPT_KEYPROVIDER_CONFIG=/tmp/ocicrypt_config.json ``` Signed-off-by: Magnus Kulke <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This lgtm. However we might want to let CDH to have its own launch configuration file to set aa_params
etc. #431
In this way, both peerpod and kata-cc could share a same interface for CDH.
relates-to: confidential-containers/cloud-api-adaptor#1637 Since peerpods will template the agent-config.toml with aa_kbc_params and /etc might be on a read-only volume, we need to make this path configurable. Signed-off-by: Magnus Kulke <[email protected]>
I think we want to look at a consolidated/consistent way of doing configuration in guest-components eventually, but I would wait for the init-data concept to be finalized to start with that. This is more like a band-aid for the moment, since a hardcoded path doesn't work with a setup in which /etc isn't writeable. kata-agent on CCv0 is frozen atm and will be for some months probably, env is a way to pass the configuration from kata-agent to CDH & AA without altering kata-agent itself. |
a124e80
to
5632b6c
Compare
relates-to: confidential-containers/cloud-api-adaptor#1637
Since peerpods will template the agent-config.toml with aa_kbc_params and /etc might be on a read-only volume, we need to make this path configurable.